Image data processing

ABSTRACT

A method and apparatus for processing image data are disclosed. The method includes the step of partitioning the image data into a plurality of data portions (μpage) for processing. Each data portion comprises a plurality of rows of pixels corresponding to at least one print swath height. The data portions are processed in a plurality of intermediate processing stages. The data portions are processed sequentially. The number of pixels per row of a data portion is determined to be just large enough ensure adequate output printing data for a given print head at all times. The processed data is then delivered to the print head in a just-in-time manner (JIT). An apparatus for processing the image data comprises an Application Specific Integrated Circuit (ASIC).

FIELD OF THE INVENTION

[0001] The present invention relates generally to the field of image data processing, and in one form to the processing of image data for printing or other means of rendering images.

BACKGROUND

[0002] Image processing architectures typically involve a number of processing stages for executing image processing, including enhancing algorithms such as half toning, depletion, error diffusion and edge smoothing. The conventional approach is that a portion of image data is completely processed by each stage before the next portion of image data can be processed. The conventional architecture makes extensive use of external memory to store and retrieve intermediate data. The intermediate data is retrieved for processing in successive stages, which necessitates frequent access of a large amount of external memory. This, in turn, dictates a need for expensive, high-speed memory. Furthermore, the large amount of data processed by the intermediate stages prevents design of a simple pipeline with internal memory. One such conventional arrangement is shown in FIG. 1.

[0003] Conventional image processing architectures, such as are used in computer printer engines, generally exhibit a number of other disadvantages, such as requiring the addition of preprocessing stages that progressively increase total processing time and reduce image processing speed.

[0004] The present invention seeks to overcome or at least reduce one or more of the problems in the prior art.

SUMMARY

[0005] The gist of the present invention involves defining a data portion of at least one physical print swath in height.

[0006] The invention discloses a method for processing image data. Image data is partitioned into a plurality of data portions. Each data portion comprises a plurality of rows of pixels corresponding to at least one print swath height. The data portions are sequentially processed in a plurality of intermediate processing stages to generate output print data.

[0007] The invention further discloses an apparatus for processing image data. The apparatus has processing means for partitioning the image data into a plurality of data portions. Each data portion comprises a plurality of rows of pixels corresponding to at least one print swath height. A plurality of intermediate processing stages sequentially process the data portions.

[0008] The intermediate processing stages can simultaneously process a different one of the partitioned data portions. In some embodiments the data processed by each intermediate stage is stored in dedicated memory of the respective intermediate stages. The number of pixels within each row of each data portion is chosen to be just large enough to ensure adequate output printing data for a given print head at all times.

[0009] The intermediate processing stages can be scheduled to process the data portions and deliver processed data to a final stage just-in-time for rendering on print media.

[0010] In some embodiments the apparatus for processing image data comprises an Application Specific Integrated Circuit (ASIC).

[0011] The invention yet further discloses a printer and method for printing.

DESCRIPTION OF THE DRAWINGS

[0012] Features and preferred embodiments of the present invention are hereinafter described with reference to the accompanying drawings in which:

[0013]FIG. 1 is a block diagram of a conventional architecture for an image processing system;

[0014]FIG. 2 shows data processing according to the image processing system of FIG. 1;

[0015]FIG. 3 is a block diagram of an architecture for an image processing system according to an embodiment of the present invention;

[0016]FIG. 4 shows data processing according to the image processing system of FIG. 3; and

[0017]FIG. 5 shows data flow through different stages of the image processing system of FIG. 3.

DETAILED DESCRIPTION

[0018] The principles of the method and apparatus for image data processing described herein have general applicability to computer printers having an array-type print head, and particularly to inkjet printers.

[0019] A print swath height is determined by the number of pixels arranged in a vertical column in a physical print head and different print heads may result in different swath heights. The height of a print swath thus represents the vertical height that can be printed by a single horizontal pass of a corresponding print head.

[0020] For purposes of this document, a micro page (or μPage) is defined as a portion of data of height one print swath or higher and an arbitrary number of columns' width. Although arbitrary, the number of columns in a μpage should be as small as possible to minimise storage memory requirements while, at the same time, of sufficient number to ensure sufficient data throughput. Specifically, the number of columns should be as small as possible to minimise dedicated memory size of the processing stages of the image processing architecture, but also of sufficient number to ensure that the final stage (e.g. nozzle or pen interface stage) will not be starved of data of a current μPage, while another μPage is being processed. In other words, the architecture needs to be able to supply data at a rate equal or faster than data consumed by the firing rate of the printer pin-head.

[0021] It will always be the case that other processes compete for memory bandwidth (e.g. CPU and I/O devices). Such processes impede the pipeline architecture memory access. The longest time such a temporary blockage can last is called pipeline memory access latency. This latency, together with the time it takes to generate the next μPage, must be lower than the time it takes to deplete the current μpage data. A rule of thumb approach is to keep the total latency at 25% to 50% of the time it takes the print head to deplete the current μPage data.

[0022] Before proceeding with a description of the embodiments of the present invention, a conventional image processing architecture is first described, with reference to FIGS. 1 and 2, to assist in better understanding the present invention.

[0023] Conventional Architecture

[0024]FIG. 1 shows a block diagram of a typical conventional architecture for an image processing system. Various conventional implementations may have a fewer or greater number of stages of image processing.

[0025] The system includes a rasterizer 110, a raster processor 120, a pixel generator 130, a pen interface 140, one or more on-chip bus interfaces 150 and a memory interface 160, all of which can be implemented in an Application Specific Integrated Circuit (ASIC) 100. Image data enters the ASIC 100 from external memory (not shown) via the memory interface 160 and the on-chip bus interfaces 150. The image data is processed by the various intermediate stages 110-130, which each receive their respective input data from the external memory and store their respective output data in the external memory, via the memory interface 160 and the on-chip bus interfaces 150. Finally, the pixel generator 130 provides data to the nozzle or pen interface 140.

[0026] Example of Data Flow and Storage Using the Conventional Architecture

[0027] The following image processing example demonstrates the data flow and storage requirements relative to each of the intermediate processing stages of the conventional architecture shown in FIG. 1. Assuming the following: Image size: 7.0″ × 8.5″ Image Resolution: 600 dpi (dpi = dots per inch) Print head type: 600 dpi, 256 Nozzles Half tone resolution: 4 bit Firing rate: 16 KHz Colors: 4

[0028] Rasterizer

[0029] The data is processed on a row-by-row basis by the rasterizer 110. The rasterizer 110 reads aRGB or RGBa data from the external memory and converts the image data to CMYK raster data. aRGB and RGBa refer to a 32-bit colour representation specifying red, green and blue components. CMYK is similarly a 32-bit representation for cyan, magenta, yellow and black colour components. These representations are predefined color spaces well known in the relevant art. $\begin{matrix} \begin{matrix} {\begin{matrix} {{{{No}.\quad {of}}\quad {dots}}\quad} \\ {{per}\quad {pixel}\quad {row}} \end{matrix} = {{paper\_ horizontal}{\_ size}*{dpi}}} \\ {= {7.0*600}} \\ {= {4,200}} \end{matrix} & (1) \\ \begin{matrix} {{{Data}\quad {per}\quad {pixel}\quad {row}} = {{{no}.\quad {of}}\quad {dots}\quad {per}\quad {row}*{{no}.\quad {of}}\quad {colors}}} \\ {= {4,200*4}} \\ {= {16,800\quad {Bytes}}} \end{matrix} & (2) \end{matrix}$

[0030] CMYK image data is converted to 4-bit half-toned image data by the rasterizer 110, a process which generates quantization. Many half-tone algorithms diffuse the error in both the forward and downward directions. Thus, the error information needs to be stored in memory for subsequent retrieval and use when processing the next row of the image. Typically, one byte of diffusion error is generated, per pixel, per color (CMYK). The total amount of diffusion error data thus equals the number of pixels multiplied by the number of colors. $\begin{matrix} \begin{matrix} {{\begin{matrix} {{{Diffusion}\quad {data}}\quad} \\ {{written}\quad {per}\quad {row}} \end{matrix} = {{{no}.\quad {of}}\quad {pixels}*{{no}.\quad {of}}\quad {colors}}}{\quad \quad}} \\ {= {4,200*4}} \\ {= {16,800\quad {Bytes}}} \end{matrix} & (3) \\ \begin{matrix} {{\begin{matrix} {{{Diffusion}\quad {data}}\quad} \\ {{read}\quad {per}\quad {row}} \end{matrix} = {{{no}.\quad {of}}\quad {pixels}*{{no}.\quad {of}}\quad {colors}}}{\quad \quad}} \\ {= {4,200*4}} \\ {= {16,800\quad {Bytes}}} \end{matrix} & (4) \\ \begin{matrix} {{\begin{matrix} {{{Half}\text{-}{toned}\quad {image}\quad {data}}\quad} \\ {{generated}\quad {per}\quad {row}} \end{matrix} = {4,200*{4\quad/2}}}\quad} \\ {= {8,400\quad {Bytes}}} \end{matrix} & (5) \end{matrix}$

$\begin{matrix} {\begin{matrix} {\begin{matrix} {{Thus},{{the}\quad {total}\quad {intermediate}}} \\ {{{data}\quad {stored}\quad {in}\quad {the}\quad {external}}\quad} \\ {{memory}\quad {per}\quad {row}} \end{matrix} = {(3) + (5)}} \\ {= {{16,800} + {8,400}}} \\ {= {25,200\quad {Bytes}}} \end{matrix}\quad} & (6) \\ \begin{matrix} {\begin{matrix} \begin{matrix} {{Total}\quad {intermediate}} \\ {{data}\quad {stored}\quad {on}\quad {the}} \end{matrix} \\ {{memory}\quad {per}\quad {swath}} \end{matrix} = {{halftoned\_ CMYK} + {{diffusion\_ data}{\_ two}{\_ rows}}}} \\ {= {\left\lbrack {(5)*256} \right\rbrack + \left\lbrack {(3)*2} \right\rbrack}} \\ {= {\left\lbrack {8,400*256} \right\rbrack + \left\lbrack {16,800*2} \right\rbrack}} \\ {= {2,184,000\quad {Bytes}}} \\ {= {\sim {2.1\quad {MB}}}} \end{matrix} & (7) \\ {\begin{matrix} {\begin{matrix} {{Total}\quad {data}\quad {written}} \\ {{and}\quad {read}\quad {per}\quad {row}} \end{matrix} = {{{RGB}\quad {data}} + {Diffusion\_ write} +}} \\ {{{Diffusion\_ read} + {{halftoned\_ CMYK}{\_ data}}}} \\ {= {(2) + (3) + (4) + (5)}} \\ {= {{16,800} + {16,800} + {16,800} + {8,400}}} \\ {= {58800\quad {Bytes}}} \end{matrix}\quad} & (8) \\ {\begin{matrix} {\begin{matrix} {{{Total}\quad {data}\quad {read}\quad {and}}\quad} \\ {{written}{\quad \quad}{per}\quad {swath}} \end{matrix} = {(8)*256}} \\ {= {15,052,800\quad {Bytes}}} \\ {= {\sim {15\quad {MB}}}} \end{matrix}\quad} & (9) \end{matrix}$

[0031] Raster Processor

[0032] The raster processor 120 waits until some predefined number of rows have been processed by the rasterizer 110, typically 16, before commencing with processing. The raster processor 120 rotates the predefined number of rows to nozzle or pen-oriented vertical bit columnized datacalled microband. The microband enables application of enrichment algorithms such as depletion.

[0033]FIG. 2 shows color planes 210, 220, 230 and 240 that correspond to the 4 printer colors and each comprise horizontal rows of rasterized pixels. An exemplary data swath 260 of one pen column high consists of a number of horizontal raster rows, each of which is a number of columns wide. The data swath 260 includes a number of microbands. An exemplary microband 250 comprises a group of 16 rasters. $\begin{matrix} \begin{matrix} \begin{matrix} {\begin{matrix} {\begin{matrix} {\quad {{Total}\quad {data}\quad {read}}} \\ {{per}\quad {microband}} \end{matrix} = {{CMYK\_ data}{\_ per}{\_ row}*16}} \\ {= {8,400*16}} \\ {= {134,400\quad {Bytes}}} \end{matrix}\quad} \\ \begin{matrix} {\begin{matrix} {{{Total}\quad {data}\quad {generated}}\quad} \\ {{per}\quad {microband}} \end{matrix} = {{CMYK\_ data}{\_ per}{\_ row}*16}} \\ {= {8,400*16}} \\ {= {134,400\quad {Bytes}}} \end{matrix} \end{matrix} \\ {\begin{matrix} {\begin{matrix} {{{Total}\quad {data}\quad {generated}}\quad} \\ {{per}\quad {swath}} \end{matrix} = {134,400*16}} \\ {= {2,150,400}} \\ {= {\sim {2.1\quad {MB}}}} \end{matrix}\quad} \end{matrix} & (10) \\ \begin{matrix} {\begin{matrix} {{{Total}\quad {Data}\quad {read}\quad {and}}\quad} \\ {{written}{\quad \quad}{per}\quad {swath}} \end{matrix} = \left( {{data\_ read} + {data\_ generated}}\quad \right.} \\ {\left. {{per}\quad {microband}} \right)*16} \\ {= {4,300,800}} \\ {= {\sim {4.2\quad {MB}}}} \end{matrix} & (11) \end{matrix}$

[0034] Pixel Generator

[0035] The pixel generator 130 reads the number of microbands required to build a swath of pixels and generates the pixel data for delivery to the nozzles or pens. The pixel data is written directly to the internal pixel memory used by the nozzle or pen interface 140. The operation can only start once a required number of microband shave been processed by the raster processor 120. It is unnecessary to generate binary pixel data for the entire swath before sending the data to the nozzles or pens for firing. As soon as sufficient binary pixel data is generated to fire few times, the data can be pumped to the nozzles or pens. The amount of intermediate data is small enough to be kept in internal memory. The only external memory access necessary is to read the microband data generated by the raster processor 120 (i.e. the previous stage). If the resolution is not multiplied in the raster processor 120, then:

Data read=˜2.1 MB per swath  (12)

CONCLUSION

[0036] $\begin{matrix} \begin{matrix} {\begin{matrix} \begin{matrix} {{The}\quad {total}\quad {transferred}} \\ {{between}\quad {external}\quad {memory}} \end{matrix} \\ {{and}\quad {the}\quad {ASIC}\quad 100} \end{matrix} = {(9) + (11) + (12)}} \\ {= {15 + 4.2 + 2.1}} \\ {= {21.3\quad {MB}}} \end{matrix} & (13) \\ \begin{matrix} {\begin{matrix} {{The}\quad {total}\quad {intermediate}} \\ {{data}\quad {stored}} \end{matrix} = {(7) + (10)}} \\ {= {2.1 + 2.1}} \\ {= {4.2\quad {MB}}} \end{matrix} & (14) \end{matrix}$

[0037] According to the above analysis, it can be seen that the intermediate data generated by the various stages of the conventional image processor, for the example given, amounts to about 4 MB. This demands that the data be stored in external memory.

[0038] A full swath is processed completely before subsequent processing of the successive swath can be undertaken.

PREFERRED EMBODIMENT

[0039] Below described is an embodiment of an image processing architecture according to the present invention.

[0040] As discussed earlier, a μPage is defined, and each such set of data is processed by the cascaded stages on a μPage-by-μPage basis, obviating the need to store large amounts of data. The μPage size (height×width), is determined arbitrarily. The height is at least one print swath height's worth. The width is determined in consideration of the amount of available dedicated memory and overall system efficiency. For example, in a system where a burst length of 8 double words will yield the best efficiency for external memory access, a 256×8 μPage might be used. Thus, each μPage will consist of 2048 pixels.

[0041]FIG. 3 shows a block diagram of an image processing architecture according to an embodiment of the present invention.

[0042] The system includes a rasterizer 310, a raster processor 320, a pixel generator 330, a nozzle or pen interface 340, one or more on-chip bus interfaces 350 and a memory interface 360. In some embodiments the rasterizer 310, the raster processor 320, the pixel generator 330, the nozzle or pen interface 340, the one or more on-chip bus interfaces 350 and the memory interface 360 are embodied in an Application Specific Integrated Circuit (ASIC) 300. Image data enters the ASIC 300 from external memory (not shown) via the memory interface 360 and the on-chip bus interfacess 350. The image data is processed by the various intermediate stages 310-330, which receive their input data directly from the previous stages, respectively. Similarly, the various intermediate stages 310-330 store their respective output data in their respective dedicated memory. In some embodiments the dedicated memory is physically located within each of the intermediate stages 310-330. The pixel generator 330 provides data to the pen interface 340. Apart from the rasterizer 310 receiving the image data from external memory via the memory interface 360 and the on-chip bus interfaces 350, no other data transfer or storage occurs externally to the ASIC 300.

[0043]FIG. 4 shows an image page broken up into smaller μPages. The image page 400 includes a full page-width swath 410 that comprises 16 μPages, each of one swath height. An exploded view of one μPage 420 is shown, of one such μPage, which is of swath height and a few pixel columns width.

[0044] The μPage boundaries are such that all image-processing relating to a specific μPage can be completed without making forward reference to μPages still to be processed. This advantageously enables pipelining of the intermediate image processing stages, thus enabling each of the intermediate stages to simultaneously process a different one of the μPages.

[0045] Just-In-Time (JIT) printing requires processing of the μpages in the pipeline to be scheduled to deliver the final print data to the nozzles or pens just before the data is actually required. This results in a significantly reduced amount of intermediate data generated, thus enabling the data to be stored in the dedicated memory of a particular intermediate stage of the ASIC 300. Consequently, the data-flow architecture of embodiments of the present invention can result in a significant increase in print speed and a significant reduction in the amount of external memory required. In addition, the lead time to begin printing is also reduced.

[0046] The disclosed architecture does not materially change the way the intermediate stages function. Certain minor changes are required to the memory interface of the intermediate processing stages to enable data access to and from the dedicated memory, rather than external memory. Changes to the processing algorithms (such as color mapping) that may deteriorate image quality are avoided.

[0047] Example of Data Flow and Storage

[0048] The following image processing example demonstrates the data flow and storage requirements relative to each of the intermediate processing stages of the architecture shown in FIG. 3. Assuming the same specifications as per the foregoing conventional example: Image size: 7.0″ × 8.5″ Image Resolution: 600 dpi (dpi = dots per inch) Print head type: 600 dpi, 256 Nozzles Halftone resolution: 4 bit Firing rate: 16 KHz Colors: 4

[0049] For these specifications, one column of data would be consumed by the print head every 16 KHz clock period=62.5 μs. If the pipeline memory access latency is, say, 100 μs (including the time it takes to generate the next μPage), a suitable μPage width would be based on 100 μs/25% (or/50%)=400 μs (or 200 μs). The width is 400 μs/62.5 μs/column=6.4 (or 3.2). Rounded this is 7 columns (or 4 columns). In the present example the μPage is chosen to be of dimension 256×8, which matches a total latency of closer to 125 μs.

[0050] Rasterizer

[0051] RGB image data is input to the rasterizer 310 from external memory via the memory interface 310 and the on-chip bus interface 350. The RGB data is converted to half-toned CMYK data.

[0052] Diffusion data for the last row of each μPage generated during processing of each swath is stored in the external memory when processing of that swath is completed. At the start of processing of the next swath, this stored diffusion data is retrieved from the external memory. So, for every swath, it is necessary to read and write diffusion error data to and from the external memory for one row. If only forward error diffusion is used, use of external memory may not be necessary. If this diffusion data generated is small enough to fit into the dedicated memory the implementer may also choose not to use external memory. $\begin{matrix} \begin{matrix} {\begin{matrix} \begin{matrix} {{RGB}\quad {data}\quad {transferred}} \\ {{from}\quad {the}\quad {external}} \end{matrix} \\ {{memory}\quad {per}\quad {swath}} \end{matrix} = {(2)*256}} \\ {= {16,800*256}} \\ {= {4,300,800\quad {Bytes}}} \end{matrix} & (15) \end{matrix}$

[0053] Intermediate Data Generated: $\begin{matrix} \begin{matrix} {\begin{matrix} {{Diffusion}\quad {data}} \\ {{per}\quad µ\quad {Page}\quad {row}} \end{matrix} = {{no\_ of}{\_ dots}{\_ per}{\_ µRow}*{no}\quad {of}\quad {{colors}.}}} \\ {= {8*4}} \\ {= {32\quad {Bytes}}} \end{matrix} & (16) \\ \begin{matrix} {{{CMYK}\quad {data}} = {{no\_ of}{\_ pixels}{\_ per}{\_ µPage}*}} \\ {{{no\_ of}{\_ colors}*{bits\_ per}{{\_ colors}/8}}} \\ {= {2048*4*{4/8}}} \\ {= {4092\quad {Bytes}}} \end{matrix} & (17) \\ \begin{matrix} {\begin{matrix} {{{Total}\quad {data}}\quad} \\ {\quad {{transferred}\quad {to}}\quad} \\ {{{and}\quad {from}}\quad} \\ {{external}\quad {memory}} \end{matrix} = {(15) + {{diffusion\_ data}{\_ for}{\_ one}{\_ row}*2}}} \\ {= {{4,300,800} + {16800*2}}} \\ {= {4,334,400}} \\ {= {\sim {4.3\quad {MB}}}} \end{matrix} & (18) \end{matrix}$

[0054] Raster Processor

[0055] The raster processor 320 may start the bit columnization as soon as a predetermined number of rows (e.g. 16 rows) have been processed by the rasterizer 310. Since the storage requirement in internal memory is not so high, raster processing may begin after the rasterizer 310 completes one μPage. Thus, there is an internal storage requirement for two μPages between the rasterizer 310 and the raster processor 320.

[0056] The amount of data output from the raster processor 320 is the same as the amount of data input to the raster processor 320, namely 2,048 pixels, unless the resolution is multiplied. If the resolution is multiplied, 4K pixels per μPage will be output from the raster processor 320. $\begin{matrix} \begin{matrix} {\begin{matrix} {{Data}\quad {generated}} \\ {{{per}\quad µ\quad {Page}}\quad} \end{matrix} = {4,092*4*{4/8}}} \\ {= {8,192\quad {Bytes}}} \end{matrix} & (19) \end{matrix}$

[0057] No external memory access is necessary if this data is stored internally.

[0058] In addition to columnization, other processes like edge smoothing or depletion can be performed by the raster processor stage 320. In certain cases, it may be desirable to accumulate data of between one and all of the columns of the preceding μPage before performing these processes. This requires more internal memory, irrespective of the architecture, and will add some very small latency to the process. The new architecture does not, however, demand any changes to edge smoothing, depletion, or other such algorithms.

[0059] Pixel Generator

[0060] The pixel generator 330 functions in the same way as in the conventional architecture, except that the data is read from internal memory instead of external memory. Binary nozzle or pen data can be generated as soon as one μpage has been processed by the raster processor 320. It may be necessary to provide internal storage space for two μPages so that the raster processor 320 can operate on one μPage while the pixel generator 330 operates on the previous μPage.

[0061]FIG. 5 shows data flow through intermediate processing stages 510 . . . 540 in the pipeline. The first μPage 550 is processed by the pen interface stage 540, the second μPage 551 is processed by the pixel generator stage 530, the third μPage 552 is processed by the raster processor stage 520 and the fourth μPage 553 is processed by the rasterizer stage 510. The pipelined architecture permits processing of the μPages 550 . . . 553 by the intermediate stages 510 . . . 540 simultaneously.

[0062] A further advantage of this architecture is that more process stages can be introduced in the pipeline. This will just add a μPage latency to the process but will not reduce the processing performance.

[0063] Memory Requirements: $\begin{matrix} \begin{matrix} {\begin{matrix} {{Rasterizer}\quad {to}\quad {Raster}} \\ {{Processor}\quad {interface}\text{:}} \\ {2\quad {µPages}} \end{matrix} = {4,092*2}} \\ {= {8,192\quad {Bytes}}} \end{matrix} & (20) \\ \begin{matrix} {{\begin{matrix} {{Raster}\quad {Processor}\quad {to}\quad {Pixel}} \\ {{Generator}\quad {interface}\text{:}} \\ {2\quad {µPages}\quad \left( {{double}\quad {resolution}} \right)} \end{matrix} = {8,192\quad*2}}\quad} \\ {= {16,382\quad {Bytes}}} \end{matrix} & (21) \\ \begin{matrix} {\begin{matrix} {{{Total}\quad {internal}}\quad} \\ {{storage}\quad {required}} \end{matrix} = {(20) + (21)}} \\ {{= {24,576\quad {Bytes}}}\quad} \\ {= {\sim {24\quad {KB}}}} \end{matrix} & (22) \\ \begin{matrix} {\begin{matrix} {{Total}\quad {external}\quad {data}} \\ {{transfer}\quad {per}\quad {swath}} \end{matrix} = (18)} \\ {= {\sim {4.3\quad {MB}}}} \end{matrix} & (23) \end{matrix}$

[0064] Data Transfer rate with the specified image size, print head size and firing rate (7″, 600 dpi, 16000 Hz): $\begin{matrix} \begin{matrix} {{{Maximum}\quad {printing}\quad {rate}} = {4,{200/16},000}} \\ {= {263\quad {ms}\quad {per}\quad {swath}}} \end{matrix} & (24) \\ \begin{matrix} {{{{No}.\quad {of}}\quad {swaths}\quad {printed}\quad {per}\quad {page}} = {8.5*{600/256}}} \\ {= {20\left( {{rounded}\quad {off}} \right)}} \end{matrix} & (25) \\ \begin{matrix} {{{{Max}.\quad {Pages}}\quad {Per}\quad {Minute}\quad ({PPM})}\quad = {60/\left\lbrack {0.263*20} \right\rbrack}} \\ {= 11.4} \end{matrix} & (26) \end{matrix}$

[0065] Considering overheads such as vertical paper movement, it may be possible to achieve 10 PPM. $\begin{matrix} \begin{matrix} {{{At}\quad 10\quad {PPM}},{{{the}\quad {time}\quad {needed}\quad {to}\quad {print}\quad {one}\quad {page}} = {60/10}}} \\ {= {6\quad {secs}}} \end{matrix} & (27) \\ \begin{matrix} {{{Time}\quad {to}\quad {print}\quad {one}\quad {swath}}\quad = {6\text{/}20}} \\ {= {300\quad {ms}}} \end{matrix} & (28) \\ \begin{matrix} {{{{{{No}.\quad {of}}\quad {pixels}\quad {per}\quad {swath}} = 4},{200\quad*256}}\quad} \\ {= {1\text{,}075\text{,}200}} \end{matrix} & (29) \\ \begin{matrix} {{{Time}\quad {to}\quad {process}\quad {one}\quad {pixel}} = {300*1\text{,}000*1\text{,}{000/1}\text{,}075\text{,}200\quad {ns}}} \\ {= {279\quad {ns}}} \end{matrix} & (30) \end{matrix}$

[0066] Conventional systems require less than 10 clocks, per pixel, per stage. Accordingly, the process speed is not limited by the individual stages.

[0067] Data transfer rate per swath using the conventional architecture: $\begin{matrix} \begin{matrix} {\begin{matrix} {{Data}\quad {transfer}\quad {rate}\quad {per}\quad {swath}} \\ {{using}\quad {the}\quad {conventional}\quad {architecture}\text{:}} \end{matrix} = {{Total}\quad {Data}\quad {transferred}\text{/}{time}}} \\ {{{to}\quad {print}\quad {one}\quad {swath}}} \\ {= {21.3/0.3}} \\ {= {71\quad {MB}\quad {per}\quad \sec}} \end{matrix} & (31) \\ \begin{matrix} {\begin{matrix} {{Data}\quad {transfer}\quad {rate}\quad {per}\quad {swath}} \\ {{using}\quad {the}\quad {pipelined}\quad \mu \quad {Page}\quad {architecture}} \end{matrix} = {{Total}\quad {Data}\quad {transferred}\text{/}{time}}} \\ {{{to}\quad {print}\quad {one}\quad {swath}}} \\ {= {4.3/0.3}} \\ {= {14.3\quad {MB}\quad {per}\quad \sec}} \end{matrix} & (32) \end{matrix}$

[0068] If 50% of the 71 MB per sec external memory bandwidth is available to the pipelined μPage architecture, it is possible to process the images at 25 PPM. TABLE 1 Comparison between the conventional architecture and pipelined architecture with μPages. Conventional Pipelined Arch. Architecture with μPages Comments Internal storage  4.2 MB   24 KB 5.3% of the current required per swath (if architecture pipelined) Total external data 21.3 MB  4.3 MB transfer per swath Data transfer rate to the  71 MB per 14.3 MB per sec For 10 PPM external memory sec Print/Processing Rate 1X 5X For any given memory bandwidth. Scalable No Yes Additional processing stage does not demand complete redesign.

CONCLUSION

[0069] From the foregoing Table 1, it can be seen that the pipelined architecture with μPages greatly reduces the external memory and bandwidth requirements. The intermediate data storage requirement between stages is significantly reduced, increasing the paper size (width) does not demand relatively larger memory resources and the time to process an image no longer limits the actual time to print.

[0070] An additional advantage is that the pipelined architecture is scalable. Adding another intermediate image-processing stage only increases processing latency and does not increase total image-processing time. Increasing the paper size (width) does not demand huge memory resources.

[0071] The foregoing describes only a few embodiments of a method and apparatus for high performance image processing, and changes can be made thereto without departing from the scope and spirit of the invention, the embodiments being illustrative and not restrictive. 

1. A method for processing image data, comprising: partitioning said image data into a plurality of data portions, each comprising a plurality of rows of pixels corresponding to at least one print swath height; and sequentially processing said data portions in a plurality of intermediate processing stages to generate output print data.
 2. The method of claim 1, wherein each of said intermediate processing stages simultaneously processes a different sequential one of said partitioned data portions.
 3. The method of claim 2, further comprising storing data processed by each intermediate stage in dedicated memory of that intermediate stage.
 4. The method of claim 3, wherein the number of pixels within each row of each of said data portions is chosen to be just large enough to ensure adequate output printing data for a given print head at all times.
 5. The method of claim 1, further comprising rendering the processed image data on print media.
 6. The method of claim 1, further comprising scheduling processing of said data portions by said intermediate processing stages to deliver processed data to a final stage just-in-time for rendering.
 7. An apparatus for processing image data, comprising: a processor that partitions said image data into a plurality of data portions, each comprising a plurality of rows of pixels corresponding to at least one print swath height; and a plurality of intermediate processing stages for sequentially processing said data portions.
 8. The apparatus of claim 7, wherein each of said intermediate processing stages include a cascaded arrangement of a rasterizer, a raster processor and a pixel generator, and wherein each of said intermediate processing stages simultaneously processes a different sequential one of said partitioned data portions.
 9. The apparatus of claim 8, further including a memory means that stores the data processed by each intermediate stage, said memory being dedicated to said intermediate processing stages.
 10. The apparatus of claim 9, wherein the number of pixels within each row of each of said data portions is chosen to be just large enough ensure adequate output printing data for a given print head at all times.
 11. The apparatus of claim 7, further including means for rendering the processed image data on print media.
 12. The apparatus of claim 7, further including processing means for scheduling processing of said data portions by said intermediate processing stages to deliver processed data to a final processing stage just-in-time for rendering.
 13. The apparatus of claim 7, wherein each of the intermediate processing stages is implemented by an Application Specific Integrated Circuit (ASIC).
 14. The method of claim 1 further comprising: supplying said processed data portions sequentially to a print head.
 15. A printer, comprising: processing means for partitioning image data into a plurality of data portions, said data portions comprising a plurality of rows of pixels corresponding to at least one print swath height; a plurality of intermediate processing stages for sequentially processing said data portions to generate output print data; and a print head sequentially receiving said processed data portions.
 16. The printer of claim 15, wherein said intermediate processing stages include a cascaded arrangement of a rasterizer, a raster processor and a pixel generator that simultaneously process a different sequential one of said partitioned data portions.
 17. The printer of claim 16, further including memory means for storing the data processed by each intermediate stage, said memory means being dedicated to said intermediate stages.
 18. The printer of claim 17, wherein the number of pixels within each row of each said data portion is chosen to be just large enough to ensure adequate output printing data for a given print head at all times.
 19. The printer of claim 15, further including means for rendering the processed image data on print media.
 20. The printer of claim 15, further including processing means for scheduling processing of said data portions by said intermediate processing stages to deliver processed data to a final processing stage just-in-time for rendering. 